Interoperability Settings

The following settings are available to be configured when the Interoperability service is enabled for a given community:

Output Message Format: The type of XML to produce when messages are output. Choices are either eBXml or CCOM (default value). CCOM messages transform the native eBXml into the appropriate CCOM message based on the event that is triggered. All Interoperability stylesheets are installed to %ProgramFiles%\Bentley\eB\Server\Engines\Interoperability\Transformations. If the standard XSLT files does not produce enough information, the XSLT files can be altered to include additional information. When changing these files, it is advisable to adhere to the Mimosa standard ( http://www.mimosa.org/ccom-bod-structure) to avoid conflicts when the receiving system validates the XML against the CCOM schema.
File Download URL: This path is used to output electronic files when the documents are approved and the "OnApprovalStatusChanged" event has been enabled. This path can either be a relative or an UNC shared path.

The type and format of the destination values for both outgoing and incoming messages are described in the table below:

Type	Required Format
Microsoft Message Queue (MSMQ)	FORMATNAME:DIRECT=OS:<SERVER_NAME>\private$\<queue_name>
Folder	C:\temp or \\<servername>\<shared_folder_name>
FTP	ftp(s)://<username>:<password>@<server>/<path> Note: When the settings have been saved and the properties window is closed, the username and password are no longer visible.
Azure	Endpoint=<your_end_point>/;SharedAccessKeyName=<KeyName>;SharedAccessKey=<value> Note: <value> is the connection string to the service bus, as configured in the shared access policies on the Azure service bus.

Note: Parameters in angle brackets (<>) are placeholders to be replaced with actual values.

Once the community is enabled, the Properties dialog box appears. For example: